Fix 50% comparison mismatch in sort_chunks_by_index (Cont.)#2575
Merged
tdophung merged 3 commits intoNVIDIA:mainfrom Jan 7, 2026
Merged
Fix 50% comparison mismatch in sort_chunks_by_index (Cont.)#2575tdophung merged 3 commits intoNVIDIA:mainfrom
tdophung merged 3 commits intoNVIDIA:mainfrom
Conversation
Signed-off-by: tdophung <tdophung@nvidia.com>
Signed-off-by: tdophung <tdophung@nvidia.com>
Signed-off-by: tdophung <tdophung@nvidia.com>
Collaborator
Author
|
/te-ci L0 jax |
Contributor
Greptile SummaryThis PR continues the work from #2566 to fix platform-dependent dtype ambiguity issues in JAX array operations. The changes add explicit Key changes:
Why this matters: Confidence Score: 5/5
Important Files Changed
Sequence DiagramsequenceDiagram
participant Test as Test Function
participant RefFunc as reference_make_chunk_sort_map
participant JAX as JAX Operations
Test->>RefFunc: Call with split_sizes, sorted_indices
RefFunc->>JAX: jnp.cumsum(split_sizes)
JAX-->>RefFunc: Return cumsum array
RefFunc->>RefFunc: Cast to int32 with .astype(jnp.int32)
RefFunc->>JAX: jnp.cumsum(sorted_sizes)
JAX-->>RefFunc: Return cumsum array
RefFunc->>RefFunc: Cast to int32 with .astype(jnp.int32)
RefFunc->>JAX: jnp.argsort(sorted_indices)
JAX-->>RefFunc: Return argsort result
RefFunc->>RefFunc: Cast to int32 with .astype(jnp.int32)
Note over RefFunc: NEW: Ensures int32 for inverse_indices
RefFunc->>JAX: jnp.arange(num_tokens, dtype=jnp.int32)
JAX-->>RefFunc: Return int32 array
Note over JAX,RefFunc: Explicit dtype prevents platform ambiguity
RefFunc->>JAX: jnp.searchsorted(src_cumsum[1:], position_indices)
JAX-->>RefFunc: Return searchsorted result
RefFunc->>RefFunc: Cast to int32 with .astype(jnp.int32)
Note over RefFunc: NEW: Ensures int32 for chunk_ids
RefFunc->>RefFunc: Compute row_id_map using int32 arrays
RefFunc-->>Test: Return int32 row_id_map
Note over Test,RefFunc: All operations now use consistent int32 dtype
|
jberchtold-nvidia
approved these changes
Jan 7, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Continure to do what PR#2566 was doing.
Fix 50% comparison mismatch in sort_chunks_by_index
When using jnp.arange to initialize array, it could be ambiguous depending on the platform to use int64 or int32, this is to explicitly specify the dtype to eliminate ambiguity, which might have caused data to be misinterpreted and read as int32 when initialized as int64, causing a 50% data mismatch
Fixes # (issue)
50% comparison mismatch in sort_chunks_by_index
Type of change
Changes
Make array init and ops specify int32 dtype for test_sort_chunk_by_index
Checklist: